Simple Mail Access Protocol
──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
top
As of 2005, SMAP is still considered experimental, and is only supported by the Courier server and Cone client.
Contents
• Features
• See also
──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
Features
• MIME attachments can be transmitted in their raw, decoded form. This allows large base64-encoded attachments to be transmitted without the 4:3 inflation that base64 encoding usually incurs.cite-ref-2[2]
• Support for sending outgoing e-mails through the SMAP connection, instead of using a separate SMTP connection to the server. An outgoing message only needs to be transmitted once to both send it and save a copy to a server-side folder.
• Unicode folder names, with native support for hierarchy.
• SMAP clients and servers can fall back to IMAP if the peer does not support SMAP.
See also
References
cite-note-11. ↑ citerefwang-xiao-lei2005Wang, Xiao Lei (2005). "Performance evaluations for multimedia applications over PR-SCTP" (PDF). University of British Columbia. pp. xii. Retrieved December 1, 2012.
cite-note-22. ↑ "SMAP". Retrieved December 1, 2012.
External links